Thanks for your contribution.

I've thought about this issue and here are a few considerations:

• Our main concern is CSS nesting at the moment, that could be targeted by a browserlist config like fully supports css-nesting using caniuse (see docs and online viewer)
• Vite uses ESBuild and the build target is not directly compatible with browserlist, we could use a library like browserlist-to-esbuild
• Currently we are using the browser from Puppeteer to generate the PDF, so the browserlist doesn't make a lot of sense for now
• A simpler solution would be to use a CSS post-processor, Vite can use LightningCSS that has a support to transpile nested CSS

Once we start migrating to a fully client PDF Generator, removing Puppeteer from the equation, it will make sense to re-evaluate having a browserlist and be sure that all our feature are correctly supported.

Sorry for the change of thoughts, what do you think about implementing instead LightningCSS with Vite, we close the issue and we re-open it when we look at full client side PDF generation?

I agree, thank you for all the explanations. When we have a full client app, we can reconsider the topic.

Closing the PR as Vite is already covering this. We will come back to a potential browserlist once we develop the full client feature.